Internet Surfer 2.0/Internet Surfer 2.0 (Wayzata Technology) (1996).iso/pc/text/mac/faqs.017

Text File | 1996-02-12 | 28.0 KB | 616 lines

Frequently Asked Questions (FAQS);faqs.017



-- How do I receive it?

The easiest way is to read comp.compilers on a system that gets usenet news.

If you don't have access to usenet news, it's also available via E-mail via
a LISTSERV forwarder at the American University.  To subscribe a person
should send e-mail to [e-mail] with one line in the mail
message (not in the subject!)  That line should read:

                        SUBSCRIBE COMPIL-L full_name
for example:
                        SUBSCRIBE COMPIL-L Ima Hacker

To get off the list the subscriber should send e-mail to the same address
with the message:       SIGNOFF COMPIL-L

If you have problems getting on or off the list, please contact me.  In
particular, if you want to use an address other than your own personal mail
address, you have to ask me to set it up.

-- How do I submit a message?

Mail it to [e-mail], also known as [e-mail]
or iecc!compilers.  I review messages nearly every day, usually including
weekends, and most messages are posted to the net within a day after I
receive them.  Occasionally when I go on vacation there may be up to a
week's delay, though I try to send out a message when that will happen.

Most net news systems will automatically turn posted messages into mail to
compilers, but some, particularly systems running notes, don't do that
correctly.  As a result, I sometimes receive hundreds of copies of a
message, all mangled slightly differently.  Please mail your contributions
unless you're sure your posting software works correctly.

When you send a message to compilers, I understand that to mean that you
want me to post it to usenet, which means it will be sent to tens of
thousands of potential readers at thousands of computers all around the
world.  It may also appear in a printed comp.compilers annual and other
books, in the ACM SIGPLAN Notices, in on-line and off-line archives,
CD-ROMs, and anywhere else that some reader decides to use it.

If you don't want me to post something, send it instead to
compilers-request.  (See below.)

-- What happens to submitted messages?

Barring mail problems, they arrive in a special mailbox here at iecc.  I
then edit the headers, trim down quoted text, fix typos and grammatical
errors, remove cute signatures, and then post them to usenet.  If I think a
message needs more editing than that, I return it to the author for
rewriting.  The main reasons I return a message are that it appears more
appropriate for another group, the message is too garbled to fix, it
contains too much quoted material relative to the amount of new material, or
I don't understand it.  I also usually return messages that directly attack
individuals, since the net has plenty of other places for ad-hominem battles.

If a message asks a simple question I sometimes answer it myself rather than
posting it.  When two or three messages arrive with the same answer to a
question, I usually post only one of them, with a comment crediting the
others.

If you send in a message and don't either see it posted or receive something
back in a few days, it probably got lost in the mail and you should contact
me, preferably via a different mail route.  I post or respond to all
messages except for ones that appear to have been sent by mistake, e.g. no
contents, or contents consisting only of another quoted message.  Sometimes
when I'm feeling exasperated I disregard messages that re-ask one of the
frequently asked questions that are answered below.

One of the most time-consuming jobs in moderating the group is trimming down
the quotes in followup articles.  In most cases, you can expect readers to
have seen the previous article, so only a few lines of quoted text should be
needed to remind the reader of the context.

I have installed a simple-minded quote filter that mechanically returns to
the sender any message that contains more quoted than unquoted lines.  Please
edit your quotes before you send in a response, to avoid having the filter
bounce your message.  Since the quote filter is pretty dumb, I do look at
bounced messages myself.  If the filter bounces a message of yours by mistake,
don't panic -- it'll get posted anyway.

``Help wanted'' and ``Position Available'' messages are collected each week
and posted in a digest every Sunday.

-- How do I respond to the author of a message?

I try to be sure that every message contains valid From: and Reply-To:
headers.  The automatic "reply" commands in most news readers let you send
mail to the author.  If you're replying to a message in a digest, be sure
to respond to the author of the particular message, not to the pseudo-author
of the digest.

Some obsolete news readers attempt to reply using the Path: header, but for
technical reasons the Path: header in a moderated message cannot point to
the actual author.  In fact, the Path: header in a compilers message is
deliberately a bad mail address, so if you have such a news reader you'll
have to edit the addresses in responses yourself and, I hope, encourage your
system manager to update your news and mail software.

Sometimes mail to an author bounces, either because a gateway isn't
working or because the return address is unregistered or otherwise bad.
Please don't ask me to forward it, since my machine is no better connected
than anyone else's.  (It's not on the Internet and only talks uucp.)  If
you send me a message obviously intended for the author of an item, I will
discard it on the theory that if it wasn't important enough for you to
send it to the right place, it isn't important enough for me, either.

-- How do I contact the moderator?

Send me mail at [e-mail].  If for some
reason your system chokes on that address (it shouldn't, it's registered)
mail to [e-mail] or [e-mail] will get to me.  I treat
messages to compilers-request as private messages to me unless they state
that they are for publication.

-- Are back issues available?

I have complete archives going back to the original mailing list in 1986.
The archives now fill about 6 megabytes, and are growing at over 200K per
month.  I update the archives at the end of each month.  People with ftp
access can get them from primost.cs.wisc.edu, (128.105.2.115) where James
Larus has kindly provided space.  The archives contain a compressed Unix
mailbox format file for each month, with names like 91-08.Z.  The file
INDEX.Z lists all of the subject lines for every message in the archives,
and in most cases is the first file you should retrieve.

The archives are available via modem from Channel One, an excellent local
BBS.  You have to register, but no payment is needed to download the
archives which are in Area 6.  (If you call more than once or twice, it
would be nice to sign up for at least the $25 trial membership.)  The 2400
BPS telephone number is [phone], and the Telebit number is +1 617
354 0470.  There is a ZIP format archive per month with names like
comp9108.zip, with the most recent archive also containing the index.

There is now a mail server at [e-mail] that can
mail you indexes, messages, and the files mentioned below.  Send it a
message containing "help" to get started.

I have also published a printed edition of the 1990 messages grouped by
thread and topic, and with some indexes, and expect to publish a 1991
edition.  Send me mail for further details, or see the message about the
book which should immediately follow this one.

-- Some Frequently Asked Questions:

NOTE: Many issues are discussed occasionally on comp.compilers, but not
frequently enought to make the FAQ sheet.  If you have a question but the
answer isn't in the FAQ, you may well be able to get good background by
reading the appropriate articles in the archive.  If you can FTP, please
at least get the index and look through it.

The various files that I mention below that I have are in the compilers
archive at primost.cs.wisc.edu, and are also available from the mail
server mentioned above.  If you can FTP them, please do so rather than
using the mail server, since the mail bandwith is quite small.

* Where can I get a C or C++ grammar in yacc?

Jim Roskind's well-known C++ grammar is in the archive, as is a C grammar
written by Jeff Lee.  Dave Jones posted a parser as message 91-09-030.
Another C grammar was posted to comp.sources.misc in June 1990, v13 i52,
archive name ansi-c_su.  GCC and G++ are based on yacc grammars, see
below.

* Where can I get the Gnu C compiler?

GCC is a high-quality free C and C++ compiler.  (Free is not the same as
public domain, see the GCC distribution for details.)  It is available in
source from from prep.ai.mit.edu.  You need an existing C compiler and
libraries to bootstrap it.

A version for 386 MS-DOS by DJ Delorie <[e-mail]> is available by FTP
from barnacle.erc.clarkson.edu or wowbagger.pc-labor.uni-bremen.de and by
mail from [e-mail] in the archive msdos/djgpp.
See messages 91-09-054 and 91-09-066.

* Are there other free C compilers?

The lcc compiler, written by people at Princeton and Bell Labs, is
available via FTP from princeton.edu.  It is supposed to generate code as
good as GCC while being considerably faster and smaller.  It comes with a
demonstration VAX code generator and documentation on the code generation
interfaces.  Production code generators for the VAX, MIPS, and Motorola
68020 are available for research use to universities willing to execute a
license agreement; the FTP package elaborates.  Lcc uses a hard-coded C
parser because it's faster than yacc.

* Where can I get a Fortran grammar in yacc?

I have a small subset parser in the archive mentioned above.  The F2C
Fortran to C translator contains a full F77 parser and is available in
source form via FTP from research.att.com and by mail from
[e-mail].

* Where can I get Modula-2, Pascal or Ada grammars in yacc?

I have one each of those, too, in the archive mentioned above, though I
haven't tried to use any of them.

* Where can I get a Cobol grammar in yacc?

Nowhere for free, as far as I can tell.  This question is asked every few
months and there has never, ever, been any positive response. Perhaps some
of the interested people could get together and write one.  The commercial
PCYACC from Abraxas (see below) comes with a bunch of sample grammars
including one for Cobol-85.

* Where can I get a Basic grammar in yacc?

Take a look at ftp.uu.net:comp.sources.unix/volume2/basic which contains
a Basic interpreter with yacc parser.

* How can I get started with yacc and lex and compiler writing in general?

By reading any of the many books on the topic.  Here are a few of them:

Aho, Sethi, and Ullman, "Compilers: Principles, Techniques, and Tools,"
Addison Wesley, 1986, ISBN 0-201-10088-6, the "dragon book".  Describes
clearly and completely lexing and parsing techniques including the ones in
yacc and lex.  The authors work or have worked at Bell Labs with Steve
Johnson and Mike Lesk, the authors of Yacc and Lex.

Alan Holub, "Compiler Design in C," Prentice-Hall, 1990, ISBN
0-13-155045-4.  A large book containing the complete source code to a
reimplementation of yacc and lex and a C compiler.  Quite well written,
too, though it has a lot of errors.  The fourth printing is supposed to
correct most of them.

Mason and Brown, "lex & yacc," O'Reilly, 1990, ISBN 0-937175-49-8.  A
short introduction with some completely worked out examples.  The writing
in the 1990 edition can be murky, but the next edition should be better.

Donnely and Stallman, "The Bison Manual," part of the on-line distrubution
of the FSF's Bison, a reimplementation of yacc.  As with everything else from
the FSF, full source code is included.

Axel T. Schreiner and H. George Friedman, Jr., "Introduction to Compiler
Construction with UNIX," Prentice-Hall, 1985.  Oriented to tutorial work.
Good for beginners.  Develops a small subset-of-C compiler through the book.
(Recommended by Eric Hughes <[e-mail]>.)  Richard Hash
<[e-mail]> comments that the book has many typographical errors, and
readers should be suspicious of the examples until they actually try them.
Richard Y. Kim <[e-mail]> reports that sources are available for
FTP as a.cs.uiuc.edu:pub/friedman/tar.

Bennett, J.P. "Introduction to Compiling Techniques - A First Course Using
Ansi C, Lex and Yacc," McGraw Hill Book Co, 1990, ISBN 0-07-707215-4.
It's intended for a first course in modern compiler techniques, is very
clearly written, and has a full chapter on YACC.  I found it to be a good
introductory text before getting into the 'Dragon book'.  (Recommended by
John Merlin <[e-mail]>.)  Source code is available
at ftp.bath.ac.uk.

Charles N. Fischer & Richard J. LeBlanc, "Crafting A Compiler", Benjamin
Cummings Publishing, Menlo Park, CA, 1988, ISBN 0-8053-3201-4.  There's
also a revised version as of 1990 or 1991 titled "Crafting A Compiler in
C", with all examples in C (the original used ADA/CS).  Erich Nahum
<[e-mail]> writes: A key compiler reference.  We used the
original to great effect in Eliot Moss' graduate compiler construction
class here at UMass.  My feeling is that Fischer & LeBlanc is a good
tutorial, and one should use Aho, Sethi, & Ullman as a reference.

Des Watson, "High-Level Languages and Their Compilers," International
Computer Science Series, Addison-Wesley Publishing Company, Wokingham
England, 1989.  Adrian Howard <[e-mail]> writes: This is
the kindest, most readable introduction to compilers at the graduate level
I have ever read - an excellent example of what textbooks should all be
like.

W.M. Waite and G. Goos, "Compiler Construction," Springer-Verlag, New
York, 1984.  Dick Grune <[e-mail]> writes: A theoretical approach to
compiler construction. Refreshing in that it gives a completely new view
of many subjects. Heavy reading, high information density.

J.P. Tremblay and P.G. Sorenson, "The Theory and Practice of Compiler
Writing," McGraw-Hill, 1985.  Dick Grune <[e-mail]> writes: Extensive
and detailed. Heavy reading. To be consulted when other sources fail.

If anyone sends in others, I'll be happy to add them to the list.

* Are there free versions of yacc and lex ?

Vern Paxton's flex is a superior reimplementation of lex.  It is available
from the same places as Gnu sources.  Berkeley Yacc is a quite compatible
PD version of yacc by Bob Corbett, available as ~ftp/pub/byacc.tar.Z on
okeeffe.berkeley.edu.  Gnu Bison is derived from an earlier version of
Corbett's work and is also fairly compatible with yacc.

* Are there versions of yacc and lex for MS-DOS?

There are several of them.  Commercial versions are MKS lex&yacc from MKS
in Waterloo Ont., [phone] or [e-mail], and PCYACC from
Abraxas Software in Portland OR, [phone].  Both include both yacc
and lex along with a lot of sample code.

The standard flex source compiles under the usual DOS compilers, although
you may want to make some of the buffers smaller.  A DOS version of Bison
is on wuarchive.wustl.edu [128.252.135.4] and other servers under
/mirrors/msdos/txtutl/bison111.zip. See message 92-07-012 for more info.

* Where I can I FTP the sources to the programs in Holub's "Compiler
Design in C" ?

You can't.  See page xvi of the Preface for ordering information.

Regards,
John Levine, comp.compilers moderator
--
Send compilers articles to [e-mail] or
{ima | spdcc | world}!iecc!compilers.  Meta-mail to compilers-request.
Xref: bloom-picayune.mit.edu comp.virus:10265 news.answers:4786
Path: bloom-picayune.mit.edu!senator-bedfellow.mit.edu!senator-bedfellow.mit.edu!usenet
From: "Kenneth R. van Wyk" <[e-mail]>
Newsgroups: comp.virus,news.answers
Subject: VIRUS-L/comp.virus Frequently Asked Questions (FAQ)
Supersedes: <[e-mail]>
Followup-To: comp.virus
Date: 25 Dec 1992 06:02:19 GMT
Organization: CERT Coordination Center
Lines: 1751
Approved: [e-mail]
Expires: 7 Feb 1993 06:02:12 GMT
Message-ID: <[e-mail]>
Reply-To: <[e-mail]>
NNTP-Posting-Host: pit-manager.mit.edu
Summary: This posting contains a list of Frequently Asked Questions,
         and their answers, about computer viruses.  It should be read
         by anyone who wishes to post to VIRUS-L/comp.virus.
X-Last-Updated: 1992/11/24

Archive-name: computer-virus-faq
Last-modified: 18 November 1992, 7:45 AM EST

           Frequently Asked Questions on VIRUS-L/comp.virus
             Last Updated: 18 November 1992, 7:45 AM EST

====================
= Preface Section: =
====================

This document is intended to answer the most Frequently Asked
Questions (FAQs) about computer viruses.  As you can see, there are
many of them!  If you are desperately seeking help after recently
discovering what appears to be a virus on your computer, consider
skimming through sections A and B to learn the essential jargon, then
concentrate on section C.

If you may have found a new virus, or are not quite sure if some file
or boot sector is infected, it is important to understand the protocol
for raising such questions, e.g. to avoid asking questions that can be
answered in this document, and to avoid sending "live" viruses except
to someone who is responsible (and even then in a safe form!).

Above all, remember the time to really worry about viruses is BEFORE
your computer gets one!

The FAQ is a dynamic document, which changes as people's questions
change.  Contributions are gratefully accepted -- please e-mail them
to me at [e-mail].  The most recent copy of this FAQ will always
be available on the VIRUS-L/comp.virus archives, including the
anonymous FTP on cert.org (192.88.209.5) in the file:
pub/virus-l/FAQ.virus-l

Ken van Wyk, moderator VIRUS-L/comp.virus

Primary contributors (in alphabetical order):
    Mark Aitchison <[e-mail]>
    Vaughan Bell <[e-mail]>
    Matt Bishop <[e-mail]>
    Vesselin Bontchev <[e-mail]>
    Olivier M.J. Crepin-Leblond <[e-mail]>
    David Chess <[e-mail]>
    John-David Childs <[e-mail]>
    Nick FitzGerald <[e-mail]>
    Claude Bersano-Hayes <[e-mail]>
    John Kida <[e-mail]>
    Donald G. Peters <[e-mail]>
    A. Padgett Peterson <[e-mail]>
    Y. Radai <[e-mail]>
    Rob Slade <[e-mail]>
    Gene Spafford <[e-mail]>
    Otto Stolz <[e-mail]>

====================

             Questions answered in this document

Section A:   Sources of Information and Anti-viral Software
             (Where can I find HELP..!)

A1)  What is VIRUS-L/comp.virus?
A2)  What is the difference between VIRUS-L and comp.virus?
A3)  How do I get onto VIRUS-L/comp.virus?
A4)  What are the guidelines for VIRUS-L?
A5)  How can I get back-issues of VIRUS-L?
A6)  What is VALERT-L?
A7)  What are the known viruses, their names, major symptoms and
     possible cures?
A8)  Where can I get free or shareware anti-virus programs?
A9)  Where can I get more information on viruses, etc.?


Section B:   Definitions
             (What is ...?)

B1)  What are computer viruses (and why should I worry about them)?
B2)  What is a Trojan Horse?
B3)  What are the main types of PC viruses?
B4)  What is a stealth virus?
B5)  What is a polymorphic virus?
B6)  What are fast and slow infectors?
B7)  What is a sparse infector?
B8)  What is a companion virus?
B9)  What is an armored virus?
B10) Miscellaneous Jargon and Abbreviations


Section C:   Virus Detection
             (Is my computer infected?  What do I do?)

C1)  What are the symptoms and indications of a virus infection?
C2)  What steps should be taken in diagnosing and identifying viruses?
C3)  What is the best way to remove a virus?
C4)  What does the <insert name here> virus do?
C5)  What are "false positives" and "false negatives"?
C6)  Could an anti-viral program itself be infected?
C7)  Where can I get a virus scanner for my Unix system?
C8)  Why does an antiviral scanner report an infection only sometimes?
C9)  Is my disk infected with the Stoned virus?
C10) I think I have detected a new virus; what do I do?
C11) CHKDSK reports 639K (or less) total memory on my system; am I
     infected?
C12) I have an infinite loop of sub-directories on my hard drive; am I
     infected?


Section D:   Protection Plans
             (What should I do to prepare against viruses?)

D1)  What is the best protection policy for my computer?
D2)  Is it possible to protect a computer system with only software?
D3)  Is it possible to write-protect the hard disk with only software?
D4)  What can be done with hardware protection?
D5)  Will setting DOS file attributes to READ ONLY protect them from
     viruses?
D6)  Will password/access control systems protect my files from
     viruses?
D7)  Will the protection systems in DR DOS work against viruses?
D8)  Will a write-protect tab on a floppy disk stop viruses?
D9)  Do local area networks (LANs) help to stop viruses or do they
     facilitate their spread?
D10) What is the proper way to make backups?


Section E:    Facts and Fibs about computer viruses
              (Can a virus...?)

E1)  Can boot sector viruses infect non-bootable floppy disks?
E2)  Can a virus hide in a PC's CMOS memory?
E3)  Can a virus hide in Extended or in Expanded RAM?
E4)  Can a virus hide in Upper Memory or in High Memory?
E5)  Can a virus infect data files?
E6)  Can viruses spread from one type of computer to another?
E7)  Can DOS viruses run on non-DOS machines (e.g. Mac, Amiga)?
E8)  Can mainframe computers be susceptible to computer viruses?
E9)  Some people say that disinfecting files is a bad idea. Is that
     true?
E10) Can I avoid viruses by avoiding shareware/free software/games?
E11) Can I contract a virus on my PC by performing a "DIR" of an
     infected floppy disk?
E12) Is there any risk in copying data files from an infected floppy
     disk to a clean PC's hard disk?
E13) Can a DOS virus survive and spread on an OS/2 system using the
     HPFS file system?
E14) Under OS/2 2.0, could a virus infected DOS session infect another
     DOS session?
E15) Can normal DOS viruses work under MS Windows?


Section F:    Miscellaneous Questions
              (I was just wondering...)

F1) How many viruses are there?
F2) How do viruses spread so quickly?
F3) What is the plural of "virus"?  "Viruses" or "viri" or "virii" or...
F4) When reporting a virus infection (and looking for assistance), what
    information should be included?
F5) How often should we upgrade our anti-virus tools to minimize
    software and labor costs and maximize our protection?


Section G:    Specific Virus and Anti-viral software Questions...

G1) I was infected by the Jerusalem virus and disinfected the infected
    files with my favorite anti-virus program.  However, Wordperfect
    and some other programs still refuse to work.  Why?
G2) I was told that the Stoned virus displays the text "Your PC is now
    Stoned" at boot time.  I have been infected by this virus several
    times, but have never seen the message.  Why?
G3) I was infected by both Stoned and Michelangelo.  Why has my
    computer became unbootable?  And why, each time I run my favorite
    scanner, does it find one of the viruses and say that it is
    removed, but when I run it again, it says that the virus is still
    there?


================================================================
= Section A.   Sources of Information and Anti-viral Software. =
================================================================

A1) What is VIRUS-L/comp.virus?

It is a discussion forum with a focus on computer virus issues.  More
specifically, VIRUS-L is an electronic mailing list and comp.virus is
a USENET newsgroup.  Both groups are moderated; all submissions are
sent to the moderator for possible inclusion in the group.  For more
information, including a copy of the posting guidelines, see the file
virus-l.README, available by anonymous FTP on cert.org in the
pub/virus-l directory.  (FTP is the Internet File Transfer Protocol,
and is described in more detail in the monthly VIRUS-L/comp.virus
archive postings - see below.)

Note that there have been, from time to time, other USENET
cross-postings of VIRUS-L, including the bit.listserv.virus-l.  These
groups are generally set up by individual site maintainers and are not
as globally accessible as VIRUS-L and comp.virus.


A2) What is the difference between VIRUS-L and comp.virus?

As mentioned above, VIRUS-L is a mailing list and comp.virus is a
newsgroup.  In addition, VIRUS-L is distributed in digest format (with
multiple e-mail postings in one large digest) and comp.virus is
distributed as individual news postings.  However, the content of the
two groups is identical.


A3) How do I get onto VIRUS-L/comp.virus?

Send e-mail to [e-mail] stating: "SUB VIRUS-L your-name".
To "subscribe" to comp.virus, simply use your favorite USENET news
reader to read the group (assuming that your site receives USENET
news).


A4) What are the guidelines for VIRUS-L?

The list of posting guidelines is available by anonymous FTP on
cert.org.  See the file pub/virus-l/virus-l.README for the most recent
copy.  In general, however, the moderator requires that discussions
are polite and non-commercial.  (Objective postings of product
availability, product reviews, etc., are fine, but commercial
advertisements are not.)  Also, requests for viruses (binary or
disassembly) are not allowed.  Technical discussions are strongly
encouraged, however, within reason.


A5) How can I get back-issues of VIRUS-L?

VIRUS-L/comp.virus includes a series of archive sites that carry all
the back issues of VIRUS-L, as well as public anti-virus software (for
various computers) and documents.  The back-issues date back to the
group's inception, 21 April 1988.  The list of archive sites is
updated monthly and distributed to the group; it includes a complete
listing of the sites, what they carry, access instructions, as well as
information on how to access FTP sites by e-mail.  The anonymous FTP
archive at cert.org carries all of the VIRUS-L back issues.  See the
file pub/virus-l/README for more information on the cert.org archive
site.


A6) What is VALERT-L?

VALERT-L is a sister group to VIRUS-L, but is intended for virus
alerts and warnings only -- NO DISCUSSIONS.  There is no direct USENET
counterpart to VALERT-L; it is a mailing list only.  All VALERT-L
postings are re-distributed to VIRUS-L/comp.virus later.  This group
is also moderated, but on a much higher priority than VIRUS-L.  The
group is monitored during business hours (East Coast, U.S.A.,
GMT-5/GMT-4); high priority off-hour postings can be made by
submitting to the group and then telephoning the CERT/CC hotline at +1
412 268 7090 -- instruct the person answering the hotline to call or
page Ken van Wyk.

Subscriptions to VALERT-L are handled identically to VIRUS-L --
contact the LISTSERV.


A7) What are the known viruses, their names, major symptoms and
    possible cures?

First of all, the reader must be aware that there is no universally
accepted naming convention for viruses, nor is there any standard
means of testing.  As a consequence nearly ALL viral information is
highly subjective and subject to interpretation and dispute.

There are several major sources of information on specific viruses.
Probably the biggest one is Patricia Hoffman's hypertext VSUM.  It
describes only DOS viruses, but almost all of them which are known
at any given time.  Unfortunately, it is regarded by many in the field
as being inaccurate, so we do not advise people to rely solely on it.
It can be downloaded from most major archive sites except SIMTEL20.

The second one is the Computer Virus Catalog, published by the Virus
Test Center in Hamburg.  It contains a highly technical description of
computer viruses for several platforms: DOS, Mac, Amiga, Atari ST,
Unix.  Unfortunately, the DOS section is quite incomplete.  The CVC
is available for anonymous FTP from ftp.informatik.uni-hamburg.de
(IP=134.100.4.42), directory pub/virus/texts/catalog.  (A copy of the
CVC is also available by anonymous FTP on cert.org in the
pub/virus-l/docs/vtc directory.)